Skip to content

Conversation

migmartri
Copy link
Member

Stores attestation in the DB instead of using the CAS backend as main storage. See #179 for the reasoning of this change.

NOTE: This is a breaking change in the sense that the control plane will stop downloading attestations in OCI, although the references to it will still be in DB (the CAS attestation REF in DB is not dropped)

Closes #179
Closes #31 since it will not be needed anymore

Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
@migmartri migmartri requested a review from danlishka June 18, 2023 16:01
Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
Copy link
Member

@danlishka danlishka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect. This will also make everything faster, as there is no need to download attestations from OCI anymore.

@migmartri migmartri merged commit b1767e6 into chainloop-dev:main Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Decouple OCI registry requirement on attestations CLI: improve UX on attestation downloading
2 participants